Fix paste detection triggering on fast typing#35
Merged
Conversation
… just showing full text after pasting to avoid rendering issues at the moment. The user can now type very fast, and it won't be picked up as a 'paste'
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
[pasted N characters]instead of the actual input[pasted N characters]summary display — pasted text now appears inline as-ispastedFullTextvariable and its special backspace handling, simplifying the input logicChanges
Services/CommandAutocomplete.cs: Replaced paste-vs-typing heuristic (previously any buffered keystroke was treated as apaste) with a threshold of 5+ buffered characters. Then removed the summary display entirely so both fast typing and real pastes
show the actual text inline.